Summary

Fixes the release-line docs refresh command added in #458. During refresh, the script temporarily removes the target version from website/versions.json before rebuilding it. The Docusaurus config was still hard-coding labels for 0.2.0 and 0.1.0, so Docusaurus could reject that transient state as an unknown version.

The config now reads website/versions.json and only applies release-line labels for versions that are currently present.

Related Issues

Follow-up to #458.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor (code improvement/cleanup)
• CI, release, or build tooling
• Other maintenance

Risk and Compatibility

Low risk. Public docs routes and labels remain unchanged during normal builds. This only makes the config tolerate the temporary versions.json state used by docs-refresh-version.

Verification

• npm --prefix website run typecheck
• temp-tree execution of website/scripts/refresh-version.mjs 0.2.0, verifying versions.json order stays 0.2.0,0.1.0
• npm --prefix website run build
• git diff --check
• pre-push make lint-ci

Reviewer Notes

This same fix is already included in the release-0.2 backport PR #460 because the bug was found while validating that branch.

Checklist

• My code follows the project style guide.
• I have performed a self-review of my own code.
• I have added or updated tests, or explained why tests are not needed.
• I have updated documentation, or explained why docs are not needed.
• I have updated generated artifacts, or confirmed none are affected.
• I have checked that this change does not log or expose secrets, tokens, credentials, keys, or raw Secret data.
• I have run the relevant local checks, or documented why they were not run.
• Any dependent changes have been merged, published, or clearly called out.